home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
sfued108.zip
/
README17.SFU
< prev
next >
Wrap
Text File
|
1992-05-29
|
19KB
|
396 lines
StormFront User Editor for the Opus CBCS
Copyright 1992 by Kevin Silcox
May 29, 1992
Disclaimer
----------
This software is available "AS IS". It is not guaranteed to work at
all. If it trashes your system or ruins your life, you have been warned.
I am not responsible for any damages incurred from the use or misuse of
this software. There is also no fee to use this software to keep with
the spirit of Opus.
You will have to get by without any real documentation until I, or
someone else writes some for this program. If you know Opus and how it
works, then this program should be pretty much self-explanatory as far
as what the actual changes to the user database do. So for now, there's
only a brief description of how to use the actual functions of the program.
Even though SFUE17 doesn't have the most user-friendly interface, I think
that its flexibility is worth the struggle you *may* go through when you
first start to use it. Enjoy!
WARNING: If you're running Opus in a multi-tasking environment then make
sure that you DO NOT Sort or Zap the database when there is a potential
for Opus to need to use the user database! (i.e. If a user calls and
tries to login.)
--=={*-------------------------------------------------*}==--
This version: 1.08 ---> For Opus v1.7x
Requires approximately 125K of Available RAM. Requires
more if using the Sort option (based on number of records
in your database --> about 28 bytes for each record, up to
a maximum of about 2300 records, plus 8 bytes per CWF). The
maximum memory requirement should be about 200K.
**> I recommend you use an EXE compressor such as PKlite in
order to reduce the program size. (About 52% with PKlite v1.13)
This program is for maintaining the user database used with
Opus. It is capable of adding users, marking them to be ReUsed,
Purged, Normal, and even Removing users marked to be Purged (Zap),
along with many other nifty features.
-*-
The program accepts a command-line argument for local and non-
local use. Entering an argument other than those arguments listed
will display a brief help screen. The arguments are as follows:
-M force Mono mode -C force Color mode -A AutoDetect
-D force DOS Output -B force BIOS Writes
-U to use a specific User file -Z to Zap the database
-X Translate IBM Graphics to -I Install defaults
Normal characters
The -M and -C options are only to force the memory address for the
direct-screen writes if the program doesn't recognize the correct video
mode. If no arguments are entered, the program will AutoDetect which
video mode to use for the direct-screen writes. If you use the DOS
option then I/O may be redirected.
The -U allows you to specify the name of the User Database file
that you want to use instead of the default USER.DAT. If you specify
just the full path without a filename, USER.DAT will be assumed (you
must have a "\" after the path though).
You may either use the -X (Translate) option from the command-line,
or use CTRL-X to toggle IBM Graphics translation ON and OFF from the
user edit screen. NOTE: When translation is turned ON, the IBM Graphics
characters in the Report will be translated also.
Use -I to change the default parameters. NOTE: Not all parameters
saved in the INI file get priority. For example, if the OPUS environment
variable is pointing to a PRM file, it will be used instead of the name
stored in the INI file. The INI file is mainly used as a backup method
to locate all the files it needs.
*--===--*
Whenever there has been a modification to the current user record,
SFUE17 will place an asterisk '*' at the top right-hand side of the
screen. There are two things that SFUE17 *may* change automatically.
If the number of times a user has called the system is zero (0), it will
be changed to one (1). Also, if the user has QkMenu (Return to Last
Menu) turned on, SFUE17 will try to make sure the menu is valid to prevent
Opus from choking. :-)
There are now two new indicators in ScrnSect 1 (as of v1.08). The
one that you probably won't see is the '[COPY]' indicator. This indicates
that you are NOT currently editing the database that Opus uses. If you
are editing the actual database that Opus uses, then you won't see the
'[COPY]'. The other indicator is '*CWF*' which indicates that the user
being displayed has a CWF file in the Opus root directory (#.?BS). This
is displayed whether you're editing a copy of the database or the real one.
When using the Inactivity timer, the program will beep at 5 second
intervals starting 20 seconds before exiting.
**==--==**
** NOTE: SFUE17 will always try to show the users' Real Name in
the Name field and their Alias in the Alias field as of
v1.08 (based on the information in the PRM file).
In the lower right-hand corner of the User Screen are the commands
that are available in all ScreenSections. Below is a brief description
of what they do:
R) Record Number: This allows you to go to a specific record number
within the database.
!) User Status: This allows you to modify the status of a user's
record. The Status can be one of the following:
Normal: This is a normal record.
Reuse : As new users are added, they will be placed in records
marked with this status instead of being added to the
end of the database.
Purge : This means that if you use the Zap function, the record
will be removed from the database. Also used by OMAN.
Update ID : This will update the caller ID number but should only be
used if the caller_ID is all zero's or in conflict with
another record.
*) Utilities: This is for maintaining the database. Options are:
Adduser: If you need to add a user, this is what you'll use.
It has gives you the option of just adding a record
at the end of the database, or searching for a record
marked with the "Reuse" status. If you choose to
search for a record to Reuse, and there is a record
marked with the Reuse status, then that record will be
cleared of its information and you may start entering
the new user information in that record.
Global : Allows you to make certain changes to specific (or all)
users. You may specify to set only a certain privilege
level, or the default is all records (record #1 will
NOT be touched). There are also sub-levels that I
don't have time to go into.
-=***=-
I feel that the options for changing Keys and Sections
may cause some confusion. With those two options there
are 4 sub-options [Exact/Set/Toggle/Unselect]:
Exact: Set each user to exactly the keys you
specify. If you only select the 'A' key,
that's the only key the users' will have
no matter what they started out with.
Set: All keys you specify will be turned ON for
each user.
Toggle: Exactly what it says... If you select the 'A'
key each users' keys will be set to the
opposite it started out as.
Unselect: The opposite of Set. It will make sure each
key you select is turned OFF.
Import : This is if you want to add t